home *** CD-ROM | disk | FTP | other *** search
- Some hints: If you want to boot A/UX from the cartridge don't forget to make
- a swap partition on it and set the kernel value SWAPCNT to the size of the
- partition. Don't make eschatology partitions - they are for backup and you
- don't need to backup the backup disk. A good way of copying files to the
- syquest is to mount it as /syquest and do
- find /dir -depth -print | cpio -puldma /syquest
- which will create /syquest/dir and copy over /dir and all subdirectories to
- the cartridge. Next time you do it, leave out the u in puldma and only files
- that have changed since the last copy will be copied. Great. This method will
- also copy over the files in /dev.
-
- More hints: You don't need to partition each cartridge. Just format it, make
- sure block 0 is blank (use dd to check or to clear it) use pname to recognize
- slice 31 and you can use it as c?d?s31. It won't work under MacOS of course.
- To be able to boot from a cartridge you will need a small MacOS partition,
- and root and swap partitions.
-
- If your formatting software does not let you create A/UX partitions then you
- will have to do them under A/UX using dp. You can also format the cartridge
- under A/UX using the diskformat command and size 512. I suggest making a
- script to use dp so that you can do more than one cartridge quickly. An
- example might be something like:
-
- dp /dev/rdsk/c4d0s31 << EOF
- I7
- a1 8 86662 SyQuest y 0 86662 0 1 y y
- wq
- EOF
-
- Make sure you always unmount the disk before removing it. Else you lose data.
- The SCSI disk driver should be modified so that the cartridge can only be
- removed when a umount is done. This is a simple modification and I'll do it
- someday when I figure out how to modify the A/UX generic disk driver to
- include my SyQuest routines in place of the sd routines.
-
- Remember to do a fsck on the device before you mount it each time. It's easy
- to forget since it is not done automatically (unless you put the drive into
- /etc/fstab). The consequences of using a disk that has not been fsck'ed can
- be serious if there are filesystem errors on the disk that fsck could have
- fixed. (Eg these errors can occur if the Mac crashes or you forget to unmount
- the disk before removing it).
-